Mobile network iot convergence

ABSTRACT

A method in a network device coupled with a packet data network (PDN) gateway of a mobile operator is described. The method includes transmitting configuration information to a low powered device gateway coupled with a plurality of low powered devices based on a received configuration request, wherein the low powered device gateway does not include a Subscriber Identity Module (SIM). The method further includes communicating with an AAA server to authenticate a selection of the plurality of low powered devices and establishing a GPRS Tunnel Protocol (GTP) tunnel with the PDN gateway. The method further includes receiving from the low powered device gateway collected data from the selection of the plurality of low powered devices and sending to the PDN gateway the collected data.

CROSS REFERENCE

This application claims the benefit of U.S. Provisional Application No.62/012,253, filed Jun. 13, 2014.

FIELD

Embodiments of the invention relate to the field of mobile networks; andmore specifically, to the mobile network and Internet of Things (IOT)convergence.

BACKGROUND

Internet Protocol version 6 (IPv6) over Low Power Wireless Personal AreaNetworks (6lowPAN) and IPv6 over Constrained Node Networks (6lo) devicesform wireless networks that can carry IPv6 packets in abridged form andconnect to the IP network via a gateway which can process the 6lowPANprotocol (disclosed in RFCs 4919, 4944, 6282, 6568, 6606, 6775). Thesedevices connect directly to the Internet or Cloud systems via an accessrouter and not through the network of a telecom operator.

SUMMARY

According to some embodiments, a method in a network device coupled witha packet data network (PDN) gateway of a mobile operator for mobilenetwork internet of things (IOT) convergence for IOT devices without asubscriber identity module (SIM) is described. The method includestransmitting configuration information to a low powered device gatewaycoupled with a plurality of low powered devices based on a receivedconfiguration request, wherein the low powered device gateway does notinclude a Subscriber Identity Module (SIM). The method further includescommunicating with an AAA server to authenticate a selection of theplurality of low powered devices and establishing a GPRS Tunnel Protocol(GTP) tunnel with the PDN gateway. The method further includes receivingfrom the low powered device gateway collected data from the selection ofthe plurality of low powered devices and sending to the PDN gateway thecollected data.

According to some embodiments, the communicating with the AAA server toauthenticate the selection of the plurality of low powered devicesincludes authenticating the selection of the plurality of low powereddevices based on a service type, a customer identifier, and the addressof the low powered device gateway, wherein the service type identifiesthe selection of the plurality of low powered devices, and wherein thecustomer identifier identifies a customer account from which theconfiguration request was received. According to some embodiments, thecommunicating with the AAA server to authenticate the selection of theplurality of low powered devices includes receiving from the AAA servera reply with an identifier of the PDN gateway.

According to some embodiments, the configuration information includes aservice type and a service action based on the received configurationrequest, wherein the service type identifies the selection of theplurality of low powered devices, and wherein the service action causesthe low powered device gateway to perform at least one of report data,start data collection, stop data collection, and establish securecommunications between the low powered device gateway and the networkelement.

According to some embodiments, the configuration information furtherincludes IP address configuration information, and wherein uponreceiving the IP address configuration information, the low powereddevice gateway is caused to configure the selection of the plurality oflow powered devices with IP addresses based on the IP addressconfiguration information.

According to some embodiments, the method further comprises for each oneof a set of one or more service types received in the configurationrequest, establishing a corresponding GTP tunnel to the PDN gateway forthat service type.

According to some embodiments, the method further comprises aggregatingthe collected data to be sent to the PDN gateway, wherein the collecteddata is aggregated based upon a type of the collected data.

According to some embodiments, the configuration request is receivedfrom a software defined networking (SDN) controller, and wherein the SDNcontroller includes an orchestrator module that receives input from acustomer for the configuration request.

According to some embodiments, the method further comprises establishinga secured channel between the network device and the low powered devicegateway based on the received configuration request.

Thus, embodiments of the invention allow for a network device toconverge for IOT devices without a subscriber identity module (SIM) witha mobile network.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may best be understood by referring to the followingdescription and accompanying drawings that are used to illustrateembodiments of the invention. In the drawings:

FIG. 1 illustrates a block diagram of a system 100 converging IOTdevices without a Subscriber Identity Module with a mobile networkaccording to an embodiment of the invention;

FIG. 2 illustrates an exemplary version of system 100 includingexemplary physical connections and layout between nodes and devices andthe protocols and security features used on the connections according toan embodiment of the invention;

FIG. 3 illustrates an exemplary 3GPP architecture 300 with a MARSservice 114 according to an embodiment of the invention;

FIG. 4 is a network transaction diagram illustrating an exemplarytransaction between the 6lo GW 102, controller 108, MARS 120, AAA 124,and operator 130 for converging IOT devices according to an embodimentof the invention;

FIG. 5 illustrates connectivity between network devices (NDs) within anexemplary network, as well as three exemplary implementations of theNDs, according to some embodiments of the invention;

FIG. 6 illustrates a general purpose control plane device 604 includinghardware 640 comprising a set of one or more processor(s) 642 (which areoften Commercial off-the-shelf (COTS) processors) and network interfacecontroller(s) 644 (NICs; also known as network interface cards) (whichinclude physical NIs 646), as well as non-transitory machine readablestorage media 648 having stored therein centralized control plane (CCP)software 650), according to some embodiments of the invention; and

FIG. 7 is a flow diagram illustrating a method for converging IOTdevices in a mobile network according to an embodiment of the invention.

DESCRIPTION OF EMBODIMENTS

The following description describes methods and apparatuses for mobilenetwork internet of things (IOT) convergence for IOT devices without aSubscriber Identity Module (SIM). In the following description, numerousspecific details such as logic implementations, opcodes, means tospecify operands, resource partitioning/sharing/duplicationimplementations, types and interrelationships of system components, andlogic partitioning/integration choices are set forth in order to providea more thorough understanding of the present invention. It will beappreciated, however, by one skilled in the art that the invention maybe practiced without such specific details. In other instances, controlstructures, gate level circuits and full software instruction sequenceshave not been shown in detail in order not to obscure the invention.Those of ordinary skill in the art, with the included descriptions, willbe able to implement appropriate functionality without undueexperimentation.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to affect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

Bracketed text and blocks with dashed borders (e.g., large dashes, smalldashes, dot-dash, and dots) may be used herein to illustrate optionaloperations that add additional features to embodiments of the invention.However, such notation should not be taken to mean that these are theonly options or optional operations, and/or that blocks with solidborders are not optional in certain embodiments of the invention.

In the following description and claims, the terms “coupled” and“connected,” along with their derivatives, may be used. It should beunderstood that these terms are not intended as synonyms for each other.“Coupled” is used to indicate that two or more elements, which may ormay not be in direct physical or electrical contact with each other,co-operate or interact with each other. “Connected” is used to indicatethe establishment of communication between two or more elements that arecoupled with each other.

An electronic device stores and transmits (internally and/or with otherelectronic devices over a network) code (which is composed of softwareinstructions and which is sometimes referred to as computer programcode) and/or data using machine-readable media, such as non-transitorymachine-readable media (e.g., machine-readable storage media such asmagnetic disks, optical disks, read only memory, flash memory devices,phase change memory) and transitory machine-readable transmission media(e.g., electrical, optical, acoustical or other form of propagatedsignals—such as carrier waves, infrared signals). Thus, an electronicdevice (e.g., a computer) includes hardware and software, such as a setof one or more processors coupled to one or more non-transitorymachine-readable storage media (to store code for execution on the setof processors and data) and a set or one or more physical networkinterface(s) to establish network connections (to transmit code and/ordata using propagating signals). One or more parts of an embodiment ofthe invention may be implemented using different combinations ofsoftware, firmware, and/or hardware.

A network device (ND) is an electronic device that communicativelyinterconnects other electronic devices on the network (e.g., othernetwork devices, end-user devices). Some network devices are “multipleservices network devices” that provide support for multiple networkingfunctions (e.g., routing, bridging, switching, Layer 2 aggregation,session border control, Quality of Service, and/or subscribermanagement), and/or provide support for multiple application services(e.g., data, voice, and video). A network device may include networkinterfaces.

A network interface (NI) may be physical or virtual; and in the contextof IP, an interface address is an IP address assigned to a NI, be it aphysical NI or virtual NI. A virtual NI may be associated with aphysical NI, with another virtual interface, or stand on its own (e.g.,a loopback interface, a point-to-point protocol interface). A NI(physical or virtual) may be numbered (a NI with an IP address) orunnumbered (a NI without an IP address). A loopback interface (and itsloopback address) is a specific type of virtual NI (and IP address) of aNE/VNE (physical or virtual) often used for management purposes; wheresuch an IP address is referred to as the nodal loopback address. The IPaddress(es) assigned to the NI(s) of a ND are referred to as IPaddresses of that ND; at a more granular level, the IP address(es)assigned to NI(s) assigned to a NE/VNE implemented on a ND can bereferred to as IP addresses of that NE/VNE.

A data store includes a non-transitory computer readable storage mediumthat stores data. The data store may include some or all of anon-transitory computer readable storage medium within an electronicdevice. In such a case, the data store may receive requests to read andwrite data to the non-transitory computer readable storage medium of thedata store from a software process source representing software codecurrently executing via one or more processors on the electronic device.The data store may also receive requests to read and write data fromsources external to the electronic device. Alternatively, the data storemay be a standalone physical device that includes the non-transitorycomputer readable storage medium and basic hardware for performing readand write operations against the non-transitory computer readablestorage medium. In such a case, the data store is coupled to externalelectronic device sources and receives requests from these externalelectronic device sources to read data from or write data to thenon-transitory computer readable storage medium of the data store. Thedata on the data store may be organized in a variety of data structures(e.g., a relational database, a directed graph structure, an associationlist) depending upon the requirements of the source that makes the readand write requests.

A cellular network or mobile network is a wireless network distributedover geographical areas called cells, each served by at least onetransmitter and receiver. These cells generally do not overlap with eachother. Some cells may transmit and receive on the same frequencies asother cells. Portable transmitter/receiver units connect to thetransmitter/receiver units for each cell to send and receive data suchas voice communication and Internet Protocol packet data. Such a systemof multiple cells may support a number of portable transmitter/receiversthat is greater than the amount of available frequency bandwidth neededby this number of portable transmitter/receivers. A portabletransmitter/receiver is able to move from one cell to another cell via ahandover mechanism that coordinates the move between the original cell,the destination cell, and the portable transmitter/receiver. Examples ofmobile network technologies include those defined by the 3rd GenerationPartnership Project, which include components such as LTE (Long TermEvolution), UMTS (Universal Mobile Telecommunications System), and GSM(Global System for Mobile Communications).

According to some embodiments of the invention, a Machine to Machine(M2M) Aggregation Routing Services (MARS) collects Internet of Things(IOT) device data from low powered device gateways (e.g., 6lo interfacesor gateways) with no subscriber identity modules (SIMs), and thenconsults an AAA (authentication, authorization and accounting) server toauthenticate the low powered device gateway. The MARS service thenestablishes a General Packet Radio Service Tunnel Protocol (GTP) tunnelwith the mobile core of the operator's mobile (cellular) network (e.g.,a packet data network (PDN) GW, evolved packet gateway (EPG) or a DataConnection Devices) to forward data from the low powered device gatewaysto the mobile core of the operator's mobile network. Thus, even thoughtypical 3GPP (3rd Generation Partnership Project) technologiesauthenticate via a subscriber identity module (SIM), the MARS serviceallows a low powered device gateway without a SIM to authenticate with amobile network. As a result, telecom operators have a method to accountfor the data from IOT devices connected to these low powered devicegateways without SIMs and they can offer or monetize services for theseIOT devices and networks. Therefore, the MARS service converges the pureIOT data of these SIM-less low powered device gateways with a mobilenetwork so that the mobile core of the mobile network may process thisdata.

FIG. 1 illustrates a block diagram of a system 100 converging IOTdevices with a mobile network according to an embodiment of theinvention. System 100 includes IOT a set of devices 120 a-n, 122 a-n,124 a-n, and 128 a-n. These devices include a variety of low powered orconstrained node devices that may utilize 6lo or 6lowPAN communicationsprotocols. Examples of IOT devices include temperature sensors, moisturesensors, light intensity sensors, utility meters, gas level sensors,switch devices, light emitters, sound sensors, vehicles, chargingpoints, field soil sensors, industrial device monitors, buildingmonitors, bridge monitors, environmental monitors, and body sensors.

System 100 includes 6lo gateways (GWs) 118 a-c. These 6lo GWs arecoupled with the IOT devices 120-28 via a link layer wirelesscommunications protocol such as Bluetooth (e.g., Bluetooth v.4.1,December 2013).

System 100 also includes a M2M aggregation routing service (MARS) 114a-b. In some embodiments, the MARS service is coupled with a controller112, the 6lo GW 118, and an operator 108. The operator 108 is a gatewayoperated by a mobile operator that is coupled with external IP networkssuch as the Internet. The MARS service is coupled with the 6lo GW 118using a Wi-Fi, Ethernet, or a similar layer 2 protocol non-mobileconnection. This connection may be part of a private networkadministered by the mobile operator.

In some embodiments, system 100 receives customer request 106 from acustomer associated with a customer account. The system 100 receivescustomer request 106 at an orchestrator 104. Orchestrator 104 may besoftware residing on a separate device coupled to controller 112, or maybe a software stored in non-transitory computer readable storage mediumof an electronic device that also includes the software for controller112. The customer request 106 identifies a service type and a serviceaction.

A service type identifies a location and/or type of IOT device that acustomer wishes to activate or enable. For example, a customer mayidentify a set of light sensors in a warehouse location. The locationsof the IOT devices may be identified using a data store of availablelocations for the selected customer within data store 132. Data store132 may also store the available types of IOT devices at the availablelocations associated with the particular customer.

A service action identifies an action that a customer has selected forthe IOT devices identified using the service type. The action can take avariety of forms, and can be different for different embodiments of theinvention. For instance, in some embodiments, a service action mayinclude, but not limited to: 1) a request for a single report of currentdata from running IOT devices (e.g., the orchestrator 104 may receive arequest to report the current temperature data from a set of sensors ina freezer); 2) a request to report the current status of the selectedIOT devices (e.g., the orchestrator 104 may receive a request to reportthe functional status and any error conditions of a set of moisturesensors; 3) a request to enable, disable, start, or stop collection ofdata from the selected IOT devices; 4) a request to enable securitybetween the selected IOT devices and the 6lo GW associated with theselected IOT devices, and/or to enable security between the 6lo GW andthe MARS service (e.g., the request may be to enable an IPSec (InternetProtocol Security) tunnel); 5) a request for the 6lo GW to re-routecommunications between the 6lo GW and the MARS service (e.g., therequest may be to re-route through an under-utilized network device);and 6) a request for configuration of the 6lo GW, including aconfiguration of selected IOT devices associated with the 6lo GW (e.g.,a configuration option may include calibration of selected IOT devicesassociated with the 6lo GW or a configuration of the reporting rate forselected IOT devices associated with the 6lo GW). Additional detailsregarding service actions are described in reference to FIG. 4.

In some embodiments, customer request 106 also includes a sub typeindicator. This sub type indicator indicates to the 6lo GW whether tosend data received from the IOT devices identified in the service typeto the operator 108 or to a fixed operator 110. Some customer requests106 do not include service actions that instruct the 6lo GW to returndata. In such a case, a sub type indicator may not be specified. A fixedoperator, such as fixed operator 110, is a non-mobile operator that mayreceive the data from the selected IOT devices indicated by the servicetype. For example, a fixed operator may be an internet service provider(ISP) or cloud service.

Once the orchestrator 104 receives the customer request 106 indicatingthe service type, service action, and optionally sub type indicator, theorchestrator 104 communicates this information to the controller 112. Inaddition, the orchestrator 104 also sends a customer identifier (ID)identifying the customer accessing the orchestrator 104 to thecontroller 112. In some embodiments, the customer ID is also known as asubscriber ID. The orchestrator 104 may determine the customer ID basedupon login information used by the customer to access the orchestrator104 and submit the customer request 106.

In some embodiments, the orchestrator 104 is an application residing onthe same physical network device as the MARS service 114. In such anembodiment, the orchestrator 104 communicates directly with the MARSservice and the controller 112 is not used.

In some embodiments, controller 112 includes a data store to determinethe correct MARS service to communicate with and to determine whichinterface or protocol to communicate with the MARS service. The physicallayout of the controller 112 will be described in more detail inrelation to FIG. 6.

The controller 112 communicates the service type, service action, subtype indicator (if provided), and customer ID to the MARS service 114.The controller 112 and the MARS service 114 may communicate over aninterface using a different protocol than that used by the customerrequest 106, and this may require conversion of the message(s) includingthe service type, service action, customer ID, and sub type indicatorprovided by the orchestrator 104 to the correct protocol. In someembodiments, the communications between the MARS service 114 and thecontroller 112 is through a non-mobile link layer protocol such asEthernet, Wi-Fi, ATM, etc.

For each customer request 106, the MARS service 114 receives the servicetype, service action, sub type indicator, and customer ID from thecontroller 112. The MARS service determines which selected 6lo GW 118includes the IOT devices identified in the service type. The informationregarding which 6lo GWs are coupled to which IOT devices at whichgeographic location may be stored in a data store 134. A set of profileproperties of the 6lo GWs and IOT devices that the MARS service 114communicates with may also be stored in data store 134. The profileproperties for each selected 6lo GW defines a set of supportedcommunications protocols, security settings, extensions, and otherconfiguration elements for the MARS service to communicate with theselected 6lo GW (e.g., the MARS service may convert the service actionit receives from the controller 112 in to a format that may beunderstood by the selected 6lo GW).

The MARS service 114 determines which of the 6lo GWs 118 to communicatewith based on the service type, and transmits one or more messages tothe selected 6lo GW 118 to cause the 6lo GW 118 to select a set of oneor more IOT devices based on the service type, and configures the IOTdevices to perform a particular action according to the service action.In some embodiments, the one or more messages transmitted by the MARSservice to the selected 6lo GW 118 also includes an Internet Protocolversion 6 (IPv6) prefix used to configure the IP addresses of theselected IOT devices identified based on the service type. An IPv6device, such as one of the selected IOT devices, configures its IPv6address using IPv6 autoconfiguration by appending the prefix to a uniqueidentifier that the device has determined to be unique based on IPv6neighbor discovery protocols. In some alternative embodiments, the IPaddresses of the IOT devices are assigned via an IPv6 (Internet Protocolversion 6) based DHCP (Dynamic Host Configuration Protocol) server(e.g., DHCP server 116) instead of via IPv6 address autoconfiguration.In another embodiment, the IOT devices might be addressed using IPv4 andthe MARS service 114 may communicate with these IOT devices using IPv4.In some embodiments, the MARS service may further support non-IP basedIOT devices by providing a proxy service.

In some embodiments, the MARS service 114 utilizes IPv6/IPv4 transitionmechanisms (e.g., Stateless IP/ICMP (Internet Control Message Protocol)Translation, RFC 6145, 6144; tunnel brokerage; 6rd, RFC 5569, 5969;Transport Relay Translation, RFC 3142; Network Address Translation 64(NAT64), RFC 6146, RFC 6877) to connect to the IPv6 based 6lo GW 118through an IPv4 network.

After the selected 6lo GW 118 receives the one or more configurationmessages from the MARS service, it sends a confirmation message to theMARS service 114 for the requested service type including anacknowledgement of configuration message receipt to the MARS service114.

Many of the service actions cause the selected 6lo GW 118 and theselected IOT devices to return IOT sensor data and/or status data to theMARS service 114 (e.g., a service action for temperature sensors tostart gathering data at a certain rate). In these cases, the MARSservice 114 forwards the received data from the 6lo GW to an operator.The MARS service 114 may be able to communicate with more than oneoperator, as each customer sending a customer request may be associatedwith separate operators. To determine which operator to send thereceived data to, the MARS service sends a request to an AAA(authentication, authorization, and accounting) server 102 to cause theAAA server 102 to determine if it has a record associated with theservice type identifier, customer ID, and IP address of the selected 6loGW corresponding to the received customer request 106. The AAA server102 includes record(s) associating an operator identifier with theunique identifier of a service type identifier, customer ID, and IPaddresses of the selected 6lo GW. If the AAA server 102 determines thata record does exist, the MARS service 114 receives from the AAA serverthe operator identifier associated with the particular service type,customer ID, and 6lo GW address. The MARS service 114 uses this operatoridentifier to determine which operator to send the received data fromthe 6lo GW to. In some embodiments, this operator information is an APN(access point name) if the operator identified is a mobile operator suchas operator 108.

In some embodiments, the MARS service sends such a request to the AAAserver 102 every time a customer request 106 is received. In alternativeembodiments, the MARS service sends such a request to the AAA server 102only if no session exists that may be identified by the service type,customer ID/subscriber ID, and 6lo GW IP address corresponding to thereceived customer request 106.

In some embodiments, each record on the AAA corresponding to uniqueservice type, customer ID, and GW address combination also includes anactive/inactive flag, and records are marked as active once a successfulrequest matching that record from the MARS service 114 is made, ormarked as inactive if the MARS service 114 communicates a terminationrequest to the AAA server 102 for the service corresponding with therecord.

The MARS service 114 may communicate with the AAA server using standardAAA protocols such as RADIUS (Remote Authentication Dial In UserService) and Diameter, with the additional information being requestedusing custom vendor extensions.

In some embodiments, the MARS service 114 receives additionalinformation from the AAA server 102, including but not limited tocompression configuration information, security configurationinformation, and quality of service (QoS) configuration information forthe unique identifier of service type, customer ID, and 6lo GW addresscombination. This additional information may be stored asattribute-value pairs on the AAA server 102 in data store 130, and maybe supplied by the operator or customer when the customer is registeredwith the operator's mobile system.

After the MARS service 114 receives this additional information, it maysend one or more configuration messages to the 6lo GW 118 based on thisadditional information. For example, the MARS service 114 may sendconfiguration messages to the 6lo GW 118 to cause it to compress thedata sent from the 6lo GW 118 to the MARS service 114 using a specifiedcompression algorithm (e.g., the deflate compression algorithm) or torequest the 6lo GW to cause the selected IOT devices to compress thedata the IOT devices send to the 6lo GW 118. As another example, theMARS service may send configuration messages to the 6lo GW 118 to causethe 6lo GW to encrypt any messages sent by the 6lo GW 118 to the MARSservice 114.

After the 6lo GW 118 receives the additional configuration message(s),the 6lo GW 118 may begin to send back any sensor data or status datafrom the IOT devices to the MARS service 114 if the service action fromthe customer request 106 indicated that the 6lo GW 118 should returndata to the MARS service 114 (e.g., a service action indicating thestart of sensor data collection).

The MARS service 114 forwards this received data from the selected 6loGW 118 to the operator identified in the operator identifier from theAAA server 102. The identified operator may be a mobile networkoperator, such as the operator 108. Alternatively, the identifiedoperator may be a fixed operator, such as fixed operator 110.

In the case where the identified operator is a mobile operator, such asoperator 108, the MARS service 114 also establishes one or more tunnels126 with the operator 108. This tunnel encapsulates the packetized databetween the MARS service and the operator 108. In some embodiments, thistunnel is a GPRS Tunneling Protocol (GTP; 3GPP TS 29.060, 32.295,29.274) tunnel.

In some embodiments, the MARS service 114 aggregates data from the IOTdevices according to the type of the data as identified in the servicetype. A type of data refers to a type of sensor or device, such astemperature measurement devices, or switch devices. Aggregation refersto the collection of multiple data elements into a single data stream orelement over a period of time, or another organizational method fordata. Each set of the aggregated data is sent to the correspondingoperator 108 using a separate GTP tunnel. In one embodiment, even if thedestination operator for two sets of the aggregated data streams is thesame, the MARS service 114 may create separate tunnels for each streamto the operator 108 if the MARS service 114 has been configured to doso. In one embodiment, if two sets of data of the same type are to besent to different operators, then they will not be aggregated together.

In some embodiments, the MARS service 114 creates a GTP tunnel for each6lo GW 118. Data from all the IOT devices associated with a 6lo GW 118are communicated to the operator 108 using a single GTP tunnel, if thatdata is destined for the same operator. Whether the MARS service 114creates a GTP tunnel per 6lo GW or per service type may depend upon apolicy set by the mobile operator. The MARS service 114, in oneembodiment, retrieves this policy information from the AAA server 102.In some embodiments, this policy is included in the customer request 106or can be obtained from a policy server (e.g., a policy and chargingrules function (PCRF) server) based on customer/service credentials, andis passed to the MARS service via the orchestrator 104 and controller112.

Once the data from the IOT devices identified by the service type in thecustomer request 106 reaches the operator 108, the operator 108 mayforward the data to the customer. The data may be forwarded andpresented to the customer via an application such as orchestrator 104.The operator 108 may also charge the customer for the data and enableQoS for the data. Further details regarding the operation of theoperator 108 will be described in relation to FIG. 3.

In some embodiments, system 100 includes multiple sets of IOT devices,such as IOT devices 120-128. Each set of IOT devices may be devices of acertain type (e.g., a temperature sensor). Multiple sets of devices maybe coupled with a single 6lo GW, depending on, for example, aconfiguration determined by an administrator or physical constraintssuch as the distance between IOT devices. Multiple 6lo GWs 118 may alsobe coupled with a single MARS service 114. Multiple MARS service modulesmay further be coupled with a single operator or single AAA server. Inthis manner, a customer may be able to access many sets of IOT devicesthrough a central interface organized by an operator.

FIG. 2 illustrates an exemplary embodiment of system 100.

In the embodiment illustrated in FIG. 2, the controller 112 is coupledwith the MARS service 114 via a private network Ethernet link 202. Thecommunications between these the controller 112 and the MARS service 114using private network Ethernet link 202 may be secured usingtechnologies such as Internet Protocol Security (IPSec; RFCs 4301, 6071,2401, etc.) based virtual private networks (VPNs) or data link layersecurity (e.g. private VLANs). A private network Ethernet link 202 isalso used between the AAA server 102 and the MARS service 114.

The MARS service may reside separately on a network device or may sharethe same network device hardware with another component of the mobilenetwork. In the depicted embodiment, the MARS service resides in anetwork device at the edge of mobile network 208. This network devicemay be, although not required, a building aggregation router device,site aggregation switching device, edge switching device, access router,or other edge access device. This network device may also include anexisting 3GPP mobile network element, such as an Evolved Packet DataGateway (ePDG; 3GPP TS 23.402 v12.4.0).

The MARS service is coupled to the operator 108, which represents amobile core gateway device such as a PDN (packet data network) GW, via aGTP (GPRS Tunneling Protocol; 3GPP TS 29.060, 32.295, 29.274) tunnel126. GTP is an IP based protocol of the mobile network. GTP may be usedwith TCP or UDP. The MARS service and the operator 108 may exchange datausing various different protocols, such as Internet Protocol (IP), X.25,or Frame Relay, based on the specifications or support of the operator108. These protocols are encapsulated by the GTP tunnel between the MARSservice and the operator 108.

The MARS service 114 is coupled to the 6lo GW 118 using a securedprivate network Ethernet link 204 in the depicted embodiment. In someembodiments, this link is not private and is instead a link in a publicnetwork (e.g., the Internet). In some embodiments, the link is not asecured link. Although the link is an Ethernet link in the depictedembodiment, the link between the MARS service 114 and the 6lo GW 118 isnot limited to Ethernet and can be implemented using other link layertechnologies (e.g., Wi-Fi (IEEE 802.11), Asynchronous Transfer Mode (ATMForum), and Point-to-Point (PPP; RFC 1161). In some embodiments, whenthe 6lo GW 118 is first connected or reconnected to the private (orpublic) network, it uses a DNS server to discover the IP address of theMARS service 114 to register with the MARS service. The MARS servicestores in its data store the IP address of the 6lo GW 118 afterregistration.

In the depicted embodiment, a secured connection may be initiated duringan initial configuration of the 6lo GW 118 by the MARS service 114 asspecified by the orchestrator 104 using a service action. Such a securedconnection may also be configured based on received information from theAAA server 102.

This secure connection may be a layer 2 secure channel implemented usinga layer 2 secure channel protocol (e.g., layer 2 MPLS (MultiprotocolLabel Switching) VPN). The secure connection may also be a layer 3secure channel such as an IPSec tunnel with Encapsulating SecurityPayload (ESP). In one embodiment, the controller 112 specifies the typeof secure channel based on the security protocols available between theMARS service 114 and the 6lo GW 118. Each secured channel that iscreated may be identified by the MARS service 114 using the customer ID,service type, tunnel ID, 6lo GW IP address, or any combination thereof.

In the depicted embodiment, the 6lo GW 118 resides outside the mobilenetwork 208 and may not be owned or operated by the mobile operator thatoperates the MARS service 114. The 6lo GW 118 is coupled with variousIOT devices, such as temperature sensors 120 and moisture sensors 122 onthe customer's agricultural farm site 210, with a secured privatewireless link 206. This link may be implemented using any short or longrange wireless communications link layer protocols or air interfaces.Examples include, but not limited to, Bluetooth, ZigBee (ZigBee 2004,2006, PRO), Z-wave (Z-Wave Alliance), Wi-Fi (IEEE 802.11), wirelesspersonal area network technology (e.g., IEEE 801.15.4), and DigitalEuropean Cordless Telecommunications (DECT). In one embodiment, thecommunications between the 6lo GW 118 and the IOT devices 120-122 aresecured.

The security used for securing link 206 may require a key to encryptcommunications between the 6lo GW and the IOT devices 120-22. This keymay be a device key provided by the vendor of the IOT device and storedon the 6lo GW 118 to allow the 6lo GW to communicate with the IOTdevice. In some embodiments, the MARS service 114 generates a key basedupon the service type and sub type indicator the MARS service 114receives from the controller 112. The MARS service 114 passes thisgenerated key to the 6lo GW 118, which then uses this generated key incombination with the device key for the connected IOT devices tosecurely communicate with the IOT devices. The controller 112 may sendto the MARS service 114 information about the key and how to generatethe key, and the method by which the 6lo GW 118 should utilize the keyto encrypt communications (e.g., the controller may request that the keybe used as a group password for a VPN connection between the IOT devicesand the 6lo GW). In some embodiments, the security is configured usingthe NETCONF (Network Configuration Protocol) protocol.

FIG. 3 illustrates an exemplary 3GPP architecture 300 with a MARSservice 114 according to an embodiment of the invention. The MARSservice 114 is coupled to the external IP networks 306 (e.g., theInternet) via the PDN GW. The MARS service 114 is coupled with the PDNGW 308 via one or more GTP tunnels 126. The PDN GW 308 may implementfunctionalities of operator 108. The MARS service utilizes variousfunctionalities of the PDN GW 308. In some embodiments, the MARS serviceutilizes the offline charging functionality of the PDN GW 308 to charge(i.e., collect a payment) for data sent and/or received according tovolume, time of day, and service type. The MARS service may also utilizethe online real time charging functionality of the PDN GW 308 to chargein real time based on service usage. In some embodiments, this chargingis performed via OFCS (offline charging system; 3GPP TS 32.240) 311 andOCS (online charging system; 3GPP TS 32.296) 310. The PDN GW 308 mayalso provide QoS or rate limiting functions on a flow level usingdedicated bearers (i.e., transport services with QoS attributes;referenced in 3GPP TS 23.107, which is hereby incorporated by reference)to data received from the MARS service 114. Each flow may correspond toa different service type and GTP tunnel as described previously. The PDNGW 308 may support multiple APNs (as described in 3GPP TS 23.003, whichis hereby incorporated by reference) and may expose this to the MARSservice 114. In such a case, the MARS service 114 may utilize thismultiple APN functionality of the PDN GW to forward data to multiplepacket data networks (PDNs; e.g., external IP networks) as defined ineach APN at the PDN GW 308.

The exemplary architecture 300 also includes an ePDG (Evolved PacketData Gateway) 302, which allows the 3GPP system to accept data fromdevices that include a SIM but which are accessing the mobile networkusing an untrusted connection. For example, for device 310 with a SIM,an access network discovery and selection function service (ANDSF) 312directs the device 310 to access untrusted Wi-Fi network 304. Uponconnecting to this network, device 310 connects to ePDG 302 using anIPSec tunnel, after which ePDG 302 establishes a GTP tunnel for thedevice 310 to PDN GW 308. The ePDG 302 may also authenticate and/orauthorize the device 310 via AAA server 102 using the identifyinginformation in the SIM for device. In some embodiments, the MARS service114 is a software component that resides with the ePDG 302 on a networkdevice.

FIG. 4 is a network transaction diagram illustrating an exemplarytransaction between the 6lo GW 102, controller 108, MARS 120, AAA 124,and operator 130 for converging IOT devices according to an embodimentof the invention.

At 402, controller 112 sends an initiation message to MARS 114. Thismessage includes the service type, service action, sub type, andcustomer ID as described above in relation to FIG. 1. In addition to theservice actions previously described, the service action may alsoinclude instructions to the MARS service 114 on how to aggregate thedata received from the IOT devices (e.g., aggregate based on the IOTdevice type type), and for service-aware control (e.g. intelligentinstructions based on a dynamic awareness of the current system). At404, the MARS service 114 sends a request including informationregarding the service type and service action to the 6lo GW 118 inresponse to the request from the controller 112. In some embodiments,this request of transaction 404 also includes IPv6 prefix information toconfigure the IP address of the IOT devices as described above.

At 406, the 6lo GW 118 responds to the request of transaction 404 with amessage confirming the service type with an acknowledgement. In someembodiments, two customer requests from different customers may have thesame service type (e.g., two requests from two different customers withdifferent customer IDs for the same sensors). In such an embodiment, theMARS service 114 may further pass the customer ID to the 6lo GW 118 andthe 6lo GW will return the customer ID to the MARS service attransaction 406 in order to identify the correct customer.

At 410, the MARS service 114 sends an authentication request to the AAAserver 102 including the unique identifier of customer ID, service type,and 6lo GW IP address. In some embodiments, this request includes arequest for additional information regarding the connection, such as thecompression configuration for the data, using custom extensions in theauthentication protocol used by the AAA server 102.

At 412, the MARS service 114 receives a response from the AAA server 102indicating that the AAA server 102 was able to locate a recordcorresponding to the unique identifier of customer ID, service type, and6lo GW IP address. The response of transaction 412 also includes, in oneembodiment, an operator identifier retrieved from the located recordidentifying the operator 108. In one embodiment, as part of transaction412, the AAA server 102 also responds to any of the additionalinformation requested via the custom extensions.

At 414, the MARS service 114 configures the 6lo GW with any additionalinformation received from the AAA server as part of transaction 412.This may include the additional configuration information provided viathe custom extensions received as part of transaction 412. For example,the additional information may include compression configurationinformation, security configuration information, and QoS configurationinformation as described above in reference to FIG. 1. The MARS service114 may send the 6lo GW 118 this additional configuration information aspart of transaction 414.

At 416, the MARS service 114 establishes a GTP tunnel with the operator108, in order to begin transferring data that it will receive from the6lo GW 118. A tunnel may be created for each service type, or for each6lo GW, using mechanisms described above.

FIG. 5 illustrates a network device 570 (ND) coupled with controller 112and having the functionality of a MARS service in an exemplary network,as well as three exemplary implementations of the ND, according to someembodiments of the invention. ND 570 is a physical device, and isconnected to other NDs via wireless or wired connections (often referredto as a link).

Two of the exemplary ND implementations in FIG. 5 are: 1) aspecial-purpose network device 502 that uses custom application—specificintegrated—circuits (ASICs) and a proprietary operating system (OS); and2) a general purpose network device 504 that uses common off-the-shelf(COTS) processors and a standard OS.

The special-purpose network device 502 includes networking hardware 510comprising compute resource(s) 512 (which typically include a set of oneor more processors), forwarding resource(s) 514 (which typically includeone or more ASICs and/or network processors), and physical networkinterfaces (NIs) 516 (sometimes called physical ports), as well asnon-transitory machine readable storage media 518 having stored thereinnetworking software 520. A physical NI is hardware in a ND through whicha network connection (e.g., wirelessly through a wireless networkinterface controller (WNIC) or through plugging in a cable to a physicalport connected to a network interface controller (NIC)) is made. Duringoperation, the networking software 520 may be executed by the networkinghardware 510 to instantiate a set of one or more networking softwareinstance(s) 522. Each of the networking software instance(s) 522, andthat part of the networking hardware 510 that executes that networksoftware instance (be it hardware dedicated to that networking softwareinstance and/or time slices of hardware temporally shared by thatnetworking software instance with others of the networking softwareinstance(s) 522), form a separate virtual network element 530A-R. Eachof the virtual network element(s) (VNEs) 530A-R includes a controlcommunication and configuration module 532A-R (sometimes referred to asa local control module or control communication module) and forwardingtable(s) 534A-R, such that a given virtual network element (e.g., 530A)includes the control communication and configuration module (e.g.,532A), a set of one or more forwarding table(s) (e.g., 534A), and thatportion of the networking hardware 510 that executes the virtual networkelement (e.g., 530A).

The special-purpose network device 502 is often physically and/orlogically considered to include: 1) a ND control plane 524 (sometimesreferred to as a control plane) comprising the compute resource(s) 512that execute the control communication and configuration module(s)532A-R; and 2) a ND forwarding plane 526 (sometimes referred to as aforwarding plane, a data plane, or a media plane) comprising theforwarding resource(s) 514 that utilize the forwarding table(s) 534A-Rand the physical NIs 516. By way of example, where the ND is a router(or is implementing routing functionality), the ND control plane 524(the compute resource(s) 512 executing the control communication andconfiguration module(s) 532A-R) is typically responsible forparticipating in controlling how data (e.g., packets) is to be routed(e.g., the next hop for the data and the outgoing physical NI for thatdata) and storing that routing information in the forwarding table(s)534A-R, and the ND forwarding plane 526 is responsible for receivingthat data on the physical NIs 516 and forwarding that data out theappropriate ones of the physical NIs 516 based on the forwardingtable(s) 534A-R.

The networking software 520 that executes on ND 502 includesinstructions that when executed by the networking hardware 510 cause theND 502 to have functionality similar to the functionality described forthe MARS service 114. The software 520 may include a controllercommunications module 524 that includes instructions to allow the ND 502to communicate with the controller 112 with functionality similar tothat described above for the MARS service 114 and the controller 112.The software 520 may include a 6lo communications module 522 thatincludes instructions to allow the ND 502 to communicate with a 6lo GWsuch as 6lo GW 118 with functionality similar to that described abovefor the MARS service 114 and the 6lo GW 118. The software 520 may alsoinclude an operator communications module 528 that includes instructionsto allow the ND 502 to communicate with the operator 108 withfunctionality similar to that described above for the MARS service 114and the operator 108.

Non-transitory machine readable storage media 518 also includes a datastore 522. This data store may provide similar functionality to thefunctionality provided by data store 134 as described above.

Returning to FIG. 5, the general purpose network device 504 includeshardware 540 comprising a set of one or more processor(s) 542 (which areoften COTS processors) and network interface controller(s) 544 (NICs;also known as network interface cards) (which include physical NIs 546),as well as non-transitory machine readable storage media 548 havingstored therein software 550. During operation, the processor(s) 542execute the software 550 to instantiate a hypervisor 554 (sometimesreferred to as a virtual machine monitor (VMM)) and one or more virtualmachines 562A-R that are run by the hypervisor 554, which arecollectively referred to as software instance(s) 552. A virtual machineis a software implementation of a physical machine that runs programs asif they were executing on a physical, non-virtualized machine; andapplications generally do not know they are running on a virtual machineas opposed to running on a “bare metal” host electronic device, thoughsome systems provide para-virtualization which allows an operatingsystem or application to be aware of the presence of virtualization foroptimization purposes. Each of the virtual machines 562A-R, and thatpart of the hardware 540 that executes that virtual machine (be ithardware dedicated to that virtual machine and/or time slices ofhardware temporally shared by that virtual machine with others of thevirtual machine(s) 562A-R), forms a separate virtual network element(s)560A-R.

The networking software 550 that executes on ND 504 includesinstructions that when executed by the processor 542 cause thevirtualized network elements 560A-R to have functionality similar to thefunctionality described for the MARS service 114. The software 550 mayinclude a controller communications module 554 that includesinstructions to allow the virtualized network elements 560A-R tocommunicate with the controller 112 with functionality similar to thatdescribed above for the MARS service 114 and the controller 112. Thesoftware 520 may include a 6lo communications module 522 that includesinstructions to allow the virtualized network elements 560A-R tocommunicate with a 6lo GW such as 6lo GW 118 with functionality similarto that described above for the MARS service 114 and the 6lo GW 118. Thesoftware 520 may also include an operator communications module 528 thatincludes instructions to allow the virtualized network elements 560A-Rto communicate with the operator 108 with functionality similar to thatdescribed above for the MARS service 114 and the operator 108.

Non-transitory machine readable storage media 548 also includes a datastores 552A-R. These data stores correspond to each of the virtualizednetwork elements 560A-R and may provide similar functionality to thefunctionality provided by data store 134 as described above.

The virtual network element(s) 560A-R perform similar functionality tothe virtual network element(s) 530A-R. For instance, the hypervisor 554may present a virtual operating platform that appears like networkinghardware 510 to virtual machine 562A, and the virtual machine 562A maybe used to implement functionality similar to the control communicationand configuration module(s) 532A and forwarding table(s) 534A (thisvirtualization of the hardware 540 is sometimes referred to as networkfunction virtualization (NFV)). Thus, NFV may be used to consolidatemany network equipment types onto industry standard high volume serverhardware, physical switches, and physical storage, which could belocated in Data centers, NDs, and customer premise equipment (CPE).However, different embodiments of the invention may implement one ormore of the virtual machine(s) 562A-R differently. For example, whileembodiments of the invention are illustrated with each virtual machine562A-R corresponding to one VNE 560A-R, alternative embodiments mayimplement this correspondence at a finer level granularity (e.g., linecard virtual machines virtualize line cards, control card virtualmachine virtualize control cards, etc.); it should be understood thatthe techniques described herein with reference to a correspondence ofvirtual machines to VNEs also apply to embodiments where such a finerlevel of granularity is used.

In certain embodiments, the hypervisor 554 includes a virtual switchthat provides similar forwarding services as a physical Ethernet switch.Specifically, this virtual switch forwards traffic between virtualmachines and the NIC(s) 544, as well as optionally between the virtualmachines 562A-R; in addition, this virtual switch may enforce networkisolation between the VNEs 560A-R that by policy are not permitted tocommunicate with each other (e.g., by honoring virtual local areanetworks (VLANs)).

The third exemplary ND implementation in FIG. 5 is a hybrid networkdevice 506, which includes both custom ASICs/proprietary OS and COTSprocessors/standard OS in a single ND or a single card within an ND. Incertain embodiments of such a hybrid network device, a platform VM(i.e., a VM that that implements the functionality of thespecial-purpose network device 502) could provide forpara-virtualization to the networking hardware present in the hybridnetwork device 506.

Regardless of the above exemplary implementations of an ND, when asingle one of multiple VNEs implemented by an ND is being considered(e.g., only one of the VNEs is part of a given virtual network) or whereonly a single VNE is currently being implemented by an ND, the shortenedterm network element (NE) is sometimes used to refer to that VNE. Alsoin all of the above exemplary implementations, each of the VNEs (e.g.,VNE(s) 530A-R, VNEs 560A-R, and those in the hybrid network device 506)receives data on the physical NIs (e.g., 516, 546) and forwards thatdata out the appropriate ones of the physical NIs (e.g., 516, 546). Forexample, a VNE implementing IP router functionality forwards IP packetson the basis of some of the IP header information in the IP packet;where IP header information includes source IP address, destination IPaddress, source port, destination port (where “source port” and“destination port” refer herein to protocol ports, as opposed tophysical ports of a ND), transport protocol (e.g., user datagramprotocol (UDP) (RFC 768, 2460, 2675, 4113, and 5405), TransmissionControl Protocol (TCP) (RFC 793 and 1180), and differentiated services(DSCP) values (RFC 2474, 2475, 2597, 2983, 3086, 3140, 3246, 3247, 3260,4594, 5865, 3289, 3290, and 3317).

The NDs of FIG. 5, for example, may form part of the Internet or aprivate network; and other electronic devices (not shown; such as enduser devices including workstations, laptops, netbooks, tablets, palmtops, mobile phones, smartphones, multimedia phones, Voice Over InternetProtocol (VOIP) phones, terminals, portable media players, GPS units,wearable devices, gaming systems, set-top boxes, Internet enabledhousehold appliances) may be coupled to the network (directly or throughother networks such as access networks) to communicate over the network(e.g., the Internet or virtual private networks (VPNs) overlaid on(e.g., tunneled through) the Internet) with each other (directly orthrough servers) and/or access content and/or services. Such contentand/or services are typically provided by one or more servers (notshown) belonging to a service/content provider or one or more end userdevices (not shown) participating in a peer-to-peer (P2P) service, andmay include, for example, public webpages (e.g., free content, storefronts, search services), private webpages (e.g., username/passwordaccessed webpages providing email services), and/or corporate networksover VPNs. For instance, end user devices may be coupled (e.g., throughcustomer premise equipment coupled to an access network (wired orwirelessly)) to edge NDs, which are coupled (e.g., through one or morecore NDs) to other edge NDs, which are coupled to electronic devicesacting as servers. However, through compute and storage virtualization,one or more of the electronic devices operating as the NDs in FIG. 5 mayalso host one or more such servers (e.g., in the case of the generalpurpose network device 504, one or more of the virtual machines 562A-Rmay operate as servers; the same would be true for the hybrid networkdevice 506; in the case of the special-purpose network device 502, oneor more such servers could also be run on a hypervisor executed by thecompute resource(s) 512); in which case the servers are said to beco-located with the VNEs of that ND.

FIG. 6 illustrates, a general purpose control plane device 604 includinghardware 640 comprising a set of one or more processor(s) 642 (which areoften COTS processors) and network interface controller(s) 644 (NICs;also known as network interface cards) (which include physical NIs 646),as well as non-transitory machine readable storage media 648 havingstored therein centralized control plane (CCP) software 650. Such acontrol plane device 604 may implement the functionality of controller112.

In embodiments that use compute virtualization, the processor(s) 642typically execute software to instantiate a hypervisor 654 (sometimesreferred to as a virtual machine monitor (VMM)) and one or more virtualmachines 662A-R that are run by the hypervisor 654; which arecollectively referred to as software instance(s) 652. A virtual machineis a software implementation of a physical machine that runs programs asif they were executing on a physical, non-virtualized machine; andapplications generally are not aware they are running on a virtualmachine as opposed to running on a “bare metal” host electronic device,though some systems provide para-virtualization which allows anoperating system or application to be aware of the presence ofvirtualization for optimization purposes. Again, in embodiments wherecompute virtualization is used, during operation an instance of the CCPsoftware 650 (illustrated as CCP instance 676A) on top of an operatingsystem 664A are typically executed within the virtual machine 662A. Inembodiments where compute virtualization is not used, the CCP instance676A on top of operating system 664A is executed on the “bare metal”general purpose control plane device 604.

The operating system 664A provides basic processing, input/output (I/O),and networking capabilities. In some embodiments, the CCP instance 676Aincludes a network controller instance 678. The network controllerinstance 678 includes a centralized reachability and forwardinginformation module instance 679 (which is a middleware layer providingthe context of the network controller 578 to the operating system 664Aand communicating with the various NEs), and an CCP application layer680 (sometimes referred to as an application layer) over the middlewarelayer (providing the intelligence required for various networkoperations such as protocols, network situational awareness, anduser—interfaces). At a more abstract level, this CCP application layer680 within the centralized control plane 576 works with virtual networkview(s) (logical view(s) of the network) and the middleware layerprovides the conversion from the virtual networks to the physical view.

In some embodiments, the functionality provided by the orchestrator 104as described above is software residing on non-transitory machinereadable storage media 648 and executing in the application layer ofcontrol plane device 604 as orchestrator IOT service application 692.

In some embodiments, the functionality provided by the controller 112 asdescribed above in regards to communications with the MARS servicebeyond that of a typical control plane device 104 is software residingon non-transitory machine readable storage media 648 and executing inthe middleware layer 679 of control plane device 604 as IOT-GWConfiguration and Service Enablement Module 690.

The centralized control plane 576 transmits relevant messages to thedata plane 580 based on CCP application layer 680 calculations andmiddleware layer mapping for each flow. A flow may be defined as a setof packets whose headers match a given pattern of bits; in this sense,traditional IP forwarding is also flow—based forwarding where the flowsdefined by the destination IP address for example; however, in otherimplementations the given pattern of bits used for a flow definition mayinclude more fields (e.g., 10 or more) in the packet headers. DifferentNDs/NEs/VNEs of the data plane 580 may receive different messages, andthus different forwarding information. The data plane 580 processesthese messages and programs the appropriate flow information andcorresponding actions in the forwarding tables (sometime referred to asflow tables) of the appropriate NE/VNEs, and then the NEs/VNEs mapincoming packets to flows represented in the forwarding tables andforward packets based on the matches in the forwarding tables.

FIG. 7 is a flow diagram illustrating a method for converging IOTdevices in a mobile network according to an embodiment of the invention.For example, method 700 can be performed by the MARS service 114. Method700 may be implemented in software, firmware, hardware, or anycombination thereof. The operations in the flow diagrams will bedescribed with reference to the exemplary embodiments of the otherfigures. However, it should be understood that the operations of theflow diagrams can be performed by embodiments of the invention otherthan those discussed with reference to the other figures, and theembodiments of the invention discussed with reference to these otherfigures can perform operations different than those discussed withreference to the flow diagrams.

Referring now to FIG. 7, at 702, the MARS service transmitsconfiguration information to a low powered device gateway coupled with aplurality of low powered devices based on a received configurationrequest, wherein the low powered device gateway does not include aSubscriber Identity Module (SIM). In some embodiments, the low powereddevice gateway is 6lo GW 118 and the low powered devices are IOT devices120-128. In some embodiments, the configuration information includes aservice type and a service action based on the received configurationrequest, wherein the service type identifies the selection of theplurality of low powered devices, and wherein the service action causesthe low powered device gateway to perform at least one of report data,start data collection, stop data collection, and establish securecommunications between the low powered device gateway and the networkelement.

In some embodiments, the configuration information further includes IPaddress configuration information, and wherein upon receiving the IPaddress configuration information, the low powered device gateway iscaused to configure the selection of the plurality of low powereddevices with IP addresses based on the IP address configurationinformation. In some embodiments, the configuration request is receivedfrom a software defined networking (SDN) controller (e.g., controller112, and wherein the SDN controller includes an orchestrator module(e.g., orchestrator 104) that receives input from a customer for theconfiguration request.

At 704, the MARS service communicates with an AAA server to authenticatea selection of the plurality of low powered devices. In someembodiments, this AAA server is AAA server 102. In some embodiments, thecommunication with the AAA server to authenticate the selection of theplurality of low powered devices includes the MARS serviceauthenticating the selection of the plurality of low powered devicesbased on a service type, a customer identifier, and the address of thelow powered device gateway, wherein the service type identifies theselection of the plurality of low powered devices, and wherein thecustomer identifier identifies a customer account from which theconfiguration request was received. In some embodiments, thecommunication with the AAA server to authenticate the selection of theplurality of low powered devices includes the MARS service receivingfrom the AAA server a reply with an identifier of the PDN gateway.

At 706, the MARS service establishes a GPRS Tunnel Protocol (GTP) tunnelwith a PDN gateway. In some embodiments, the PDN gateway is operator108. In some embodiments, the MARS service, for each of a set of one ormore service types received in the configuration request, establishes acorresponding GTP tunnel to the PDN gateway for that service type.

At 708, the MARS service receives from the low powered device gatewaycollected data from a selection of the plurality of low powered devices.At 710, the MARS service sends the collected data to the PDN gateway. Insome embodiments, the MARS service aggregates the collected data to besent to the PDN gateway, wherein the collected data is aggregated basedupon a type of the collected data.

In some embodiments, the MARS service establishes a secured channelbetween the MARS service and the low powered device gateway based on thereceived configuration request.

While the invention has been described in terms of several embodiments,those skilled in the art will recognize that the invention is notlimited to the embodiments described, can be practiced with modificationand alteration within the spirit and scope of the appended claims. Thedescription is thus to be regarded as illustrative instead of limiting.

1. A method in a network device coupled with a packet data network (PDN)gateway of a mobile operator, comprising: transmitting configurationinformation to a low powered device gateway coupled with a plurality oflow powered devices based on a received configuration request, whereinthe low powered device gateway does not include a Subscriber IdentityModule (SIM); communicating with an AAA server to authenticate aselection of the plurality of low powered devices; establishing a GPRSTunnel Protocol (GTP) tunnel with the PDN gateway; receiving from thelow powered device gateway collected data from the selection of theplurality of low powered devices; and sending to the PDN gateway thecollected data.
 2. The method of claim 1, wherein the communicating withthe AAA server to authenticate the selection of the plurality of lowpowered devices includes authenticating the selection of the pluralityof low powered devices based on a service type, a customer identifier,and the address of the low powered device gateway, wherein the servicetype identifies the selection of the plurality of low powered devices,and wherein the customer identifier identifies a customer account fromwhich the configuration request was received.
 3. The method of claim 1,wherein the communicating with the AAA server to authenticate theselection of the plurality of low powered devices includes receivingfrom the AAA server a reply with an identifier of the PDN gateway. 4.The method of claim 1, wherein the configuration information includes aservice type and a service action based on the received configurationrequest, wherein the service type identifies the selection of theplurality of low powered devices, and wherein the service action causesthe low powered device gateway to perform at least one of report data,start data collection, stop data collection, and establish securecommunications between the low powered device gateway and the networkdevice.
 5. The method of claim 4, wherein the configuration informationfurther includes IP address configuration information, and wherein uponreceiving the IP address configuration information, the low powereddevice gateway is caused to configure the selection of the plurality oflow powered devices with IP addresses based on the IP addressconfiguration information.
 6. The method of claim 4, further comprisingfor each one of a set of one or more service types received in theconfiguration request, establishing a corresponding GTP tunnel to thePDN gateway for that service type.
 7. The method of claim 1, furthercomprising aggregating the collected data to be sent to the PDN gateway,wherein the collected data is aggregated based upon a type of thecollected data.
 8. The method of claim 1, wherein the configurationrequest is received from a software defined networking (SDN) controller,and wherein the SDN controller includes an orchestrator module thatreceives input from a customer for the configuration request.
 9. Themethod of claim 1, further comprising establishing a secured channelbetween the network device and the low powered device gateway based onthe received configuration request.
 10. A network device coupled with apacket data network (PDN) of a mobile operator, comprising: a processorand a memory, said memory containing instructions executable by theprocessor whereby the network device is operative to: transmitconfiguration information to a low powered device gateway coupled with aplurality of low powered devices based on a received configurationrequest, wherein the low powered device gateway does not include aSubscriber Identity Module (SIM); communicate with an AAA server toauthenticate a selection of the plurality of low powered devices;establish a GPRS Tunnel Protocol (GTP) tunnel with the PDN gateway;receive from the low powered device gateway collected data from theselection of the plurality of low powered devices; and send to the PDNgateway the collected data.
 11. The network device of claim 10, whereinthe communication with the AAA server to authenticate the selection ofthe plurality of low powered devices includes instructions executable bythe processor whereby the network device is operative to authenticatethe selection of the plurality of low powered devices based on a servicetype, a customer identifier, and the address of the low powered devicegateway, wherein the service type identifies the selection of theplurality of low powered devices, and wherein the customer identifieridentifies a customer account from which the configuration request wasreceived.
 12. The network device of claim 10, wherein the communicationwith the AAA server to authenticate the selection of the plurality oflow powered devices includes instructions executable by the processorwhereby the network device is operative to receive from the AAA server areply with an identifier of the PDN gateway.
 13. The network device ofclaim 10, wherein the configuration information includes a service typeand a service action based on the received configuration request,wherein the service type identifies the selection of the plurality oflow powered devices, and wherein the service action causes the lowpowered device gateway to perform at least one of report data, startdata collection, stop data collection, and establish securecommunications between the low powered device gateway and the networkelement.
 14. The network device of claim 13, wherein the configurationinformation further includes IP address configuration information, andwherein upon receiving the IP address configuration information, the lowpowered device gateway is caused to configure the selection of theplurality of low powered devices with IP addresses based on the IPaddress configuration information.
 15. The network device of claim 13,further comprising instructions executable by the processor whereby thenetwork device is operative to, for each one of a set of one or moreservice types received in the configuration request, establish acorresponding GTP tunnel to the PDN gateway for that service type. 16.The network device of claim 10, further comprising instructionsexecutable by the processor whereby the network device is operative toaggregate the collected data to be sent to the PDN gateway, wherein thecollected data is aggregated based upon a type of the collected data.17. The network device of claim 10, wherein the configuration request isreceived from a software defined networking (SDN) controller, andwherein the SDN controller includes an orchestrator module that receivesinput from a customer for the configuration request.
 18. The networkdevice of claim 10, further comprising instructions executable by theprocessor whereby the network device is operative to establish a securedchannel between the network device and the low powered device gatewaybased on the received configuration request.
 19. A non-transitorycomputer-readable storage medium having instructions stored therein,wherein the instructions, when executed by a processor of a networkdevice coupled with a packet data network (PDN) gateway of a mobileoperator, cause the processor to perform operations comprising:transmitting configuration information to a low powered device gatewaycoupled with a plurality of low powered devices based on a receivedconfiguration request, wherein the low powered device gateway does notinclude a Subscriber Identity Module (SIM); communicating with an AAAserver to authenticate a selection of the plurality of low powereddevices; establishing a GPRS Tunnel Protocol (GTP) tunnel with the PDNgateway; receiving from the low powered device gateway collected datafrom the selection of the plurality of low powered devices; and sendingto the PDN gateway the collected data.
 20. The non-transitorycomputer-readable storage medium of claim 19, wherein the communicatingwith the AAA server to authenticate the selection of the plurality oflow powered devices includes authenticating the selection of theplurality of low powered devices based on a service type, a customeridentifier, and the address of the low powered device gateway, whereinthe service type identifies the selection of the plurality of lowpowered devices, and wherein the customer identifier identifies acustomer account from which the configuration request was received. 21.The non-transitory computer-readable storage medium of claim 19, whereinthe communicating with the AAA server to authenticate the selection ofthe plurality of low powered devices includes receiving from the AAAserver a reply with an identifier of the PDN gateway.
 22. Thenon-transitory computer-readable storage medium of claim 19, wherein theconfiguration information includes a service type and a service actionbased on the received configuration request, wherein the service typeidentifies the selection of the plurality of low powered devices, andwherein the service action causes the low powered device gateway toperform at least one of report data, start data collection, stop datacollection, and establish secure communications between the low powereddevice gateway and the network element.
 23. The non-transitorycomputer-readable storage medium of claim 22, wherein the configurationinformation further includes IP address configuration information, andwherein upon receiving the IP address configuration information, the lowpowered device gateway is caused to configure the selection of theplurality of low powered devices with IP addresses based on the IPaddress configuration information.
 24. The non-transitorycomputer-readable storage medium of claim 22, further comprising foreach one of a set of one or more service types received in theconfiguration request, establishing a corresponding GTP tunnel to thePDN gateway for that service type.
 25. The non-transitorycomputer-readable storage medium of claim 19, further comprisingaggregating the collected data to be sent to the PDN gateway, whereinthe collected data is aggregated based upon a type of the collecteddata.
 26. The non-transitory computer-readable storage medium of claim19, wherein the configuration request is received from a softwaredefined networking (SDN) controller, and wherein the SDN controllerincludes an orchestrator module that receives input from a customer forthe configuration request.
 27. The non-transitory computer-readablestorage medium of claim 19, further comprising establishing a securedchannel between the network device and the low powered device gatewaybased on the received configuration request.